Method and apparatus for authorizing pedestrian user equipment in wireless communication system

ABSTRACT

For vehicle-to-everything (V2X) communication, an eNodeB (eNB) receives authorization information for a pedestrian UE which indicates whether a user equipment (UE) is authorized as the pedestrian UE. Upon receiving the authorization information for the pedestrian UE, the eNB may authorize the UE as the pedestrian UE or not according to the received authorization information, and decide a resource allocation mode for the authorized pedestrian UE.

CROSS-REFERENCE TO RELATED APPLICATION

Pursuant to 35 U.S.C. §119(e), this application claims the benefit ofU.S. Provisional Patent Application No. 62/313,702, filed on Mar. 25,2016, the contents of which are hereby incorporated by reference hereinin its entirety.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates to wireless communications, and moreparticularly, to a method and apparatus for authorizing a pedestrianuser equipment (UE) in a wireless communication system.

Related Art

3rd generation partnership project (3GPP) long-term evolution (LTE) is atechnology for enabling high-speed packet communications. Many schemeshave been proposed for the LTE objective including those that aim toreduce user and provider costs, improve service quality, and expand andimprove coverage and system capacity. The 3GPP LTE requires reduced costper bit, increased service availability, flexible use of a frequencyband, a simple structure, an open interface, and adequate powerconsumption of a terminal as an upper-level requirement.

The pace of LTE network deployment is accelerating all over the world,which enables more and more advanced services and Internet applicationsmaking use of the inherent benefits of LTE, such as higher data rate,lower latency and enhanced coverage. Widely deployed LTE-based networkprovides the opportunity for the vehicle industry to realize the conceptof ‘connected cars’. By providing a vehicle with an access to the LTEnetwork, a vehicle can be connected to the Internet and other vehiclesso that a broad range of existing or new services can be envisaged.Vehicle manufacturers and cellular network operators show stronginterests in vehicle wireless communications for proximity safetyservices as well as commercial applications. LTE-basedvehicle-to-everything (V2X) study is urgently desired from marketrequirement, and the market for vehicle-to-vehicle (V2V) communicationin particular is time sensitive. There are many research projects andfield tests of connected vehicles in some countries or regions, such asUS/Europe/Japan/Korea.

V2X includes a vehicle-to-vehicle (V2V), covering LTE-basedcommunication between vehicles, vehicle-to-pedestrian (V2P), coveringLTE-based communication between a vehicle and a device carried by anindividual (e.g. handheld terminal carried by a pedestrian, cyclist,driver or passenger), and vehicle-to-infrastructure/network (V2I/N),covering LTE-based communication between a vehicle and a roadside unit(RSU)/network. A RSU is a transportation infrastructure entity (e.g. anentity transmitting speed notifications) implemented in an eNodeB (eNB)or a stationary UE.

SUMMARY OF THE INVENTION

The present invention provides a method and apparatus for authorizing apedestrian user equipment (UE) in a wireless communication system. Thepresent invention provides a S1 and X2 enhancement for vehicle UE androad side unit (RSU) UE, pedestrian UE authentication procedure.

In an aspect, a method for receiving authorization information forvehicle-to-everything (V2X) communication by an eNodeB (eNB) in awireless communication system is provided. The method includes receivingauthorization information for a pedestrian user equipment (UE) whichindicates whether a UE is authorized as the pedestrian UE.

In another aspect, an eNodeB (eNB) in a wireless communication system isprovided. The method includes a memory, and a processor, coupled to thememory, that receives authorization information for a pedestrian userequipment (UE) which indicates whether a UE is authorized as thepedestrian UE.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows LTE system architecture.

FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and atypical EPC.

FIG. 3 shows a block diagram of a user plane protocol stack of an LTEsystem.

FIG. 4 shows a block diagram of a control plane protocol stack of an LTEsystem.

FIG. 5 shows an example of a physical channel structure.

FIG. 6 shows an example of an architecture for V2X communication.

FIG. 7 shows a method for receiving authorization information for V2Xcommunication according to an embodiment of the present invention.

FIG. 8 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.

FIG. 9 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.

FIG. 10 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.

FIG. 11 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.

FIG. 12 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.

FIG. 13 shows a communication system to implement an embodiment of thepresent invention.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

The technology described below can be used in various wirelesscommunication systems such as code division multiple access (CDMA),frequency division multiple access (FDMA), time division multiple access(TDMA), orthogonal frequency division multiple access (OFDMA), singlecarrier frequency division multiple access (SC-FDMA), etc. The CDMA canbe implemented with a radio technology such as universal terrestrialradio access (UTRA) or CDMA-2000. The TDMA can be implemented with aradio technology such as global system for mobile communications(GSM)/general packet ratio service (GPRS)/enhanced data rate for GSMevolution (EDGE). The OFDMA can be implemented with a radio technologysuch as institute of electrical and electronics engineers (IEEE) 802.11(Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA), etc.IEEE 802.16m is an evolution of IEEE 802.16e, and provides backwardcompatibility with an IEEE 802.16-based system. The UTRA is a part of auniversal mobile telecommunication system (UMTS). 3rd generationpartnership project (3GPP) long term evolution (LTE) is a part of anevolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA indownlink and uses the SC-FDMA in uplink. LTE-advance (LTE-A) is anevolution of the 3GPP LTE.

For clarity, the following description will focus on the LTE-A. However,technical features of the present invention are not limited thereto.

FIG. 1 shows LTE system architecture. The communication network iswidely deployed to provide a variety of communication services such asvoice over internet protocol (VoIP) through IMS and packet data.

Referring to FIG. 1, the LTE system architecture includes one or moreuser equipment (UE; 10), an evolved-UMTS terrestrial radio accessnetwork (E-UTRAN) and an evolved packet core (EPC). The UE 10 refers toa communication equipment carried by a user. The UE 10 may be fixed ormobile, and may be referred to as another terminology, such as a mobilestation (MS), a user terminal (UT), a subscriber station (SS), awireless device, etc.

The E-UTRAN includes one or more evolved node-B (eNB) 20, and aplurality of UEs may be located in one cell. The eNB 20 provides an endpoint of a control plane and a user plane to the UE 10. The eNB 20 isgenerally a fixed station that communicates with the UE 10 and may bereferred to as another terminology, such as a base station (BS), anaccess point, etc. One eNB 20 may be deployed per cell.

Hereinafter, a downlink (DL) denotes communication from the eNB 20 tothe UE 10, and an uplink (UL) denotes communication from the UE 10 tothe eNB 20. In the DL, a transmitter may be a part of the eNB 20, and areceiver may be a part of the UE 10. In the UL, the transmitter may be apart of the UE 10, and the receiver may be a part of the eNB 20.

The EPC includes a mobility management entity (MME) and a servinggateway (S-GW). The MME/S-GW 30 may be positioned at the end of thenetwork. For clarity, MME/S-GW 30 will be referred to herein simply as a“gateway,” but it is understood that this entity includes both the MMEand S-GW. A packet data network (PDN) gateway (P-GW) may be connected toan external network.

The MME provides various functions including non-access stratum (NAS)signaling to eNBs 20, NAS signaling security, access stratum (AS)security control, inter core network (CN) node signaling for mobilitybetween 3GPP access networks, idle mode UE reachability (includingcontrol and execution of paging retransmission), tracking area listmanagement (for UE in idle and active mode), packet data network (PDN)gateway (P-GW) and S-GW selection, MME selection for handovers with MMEchange, serving GPRS support node (SGSN) selection for handovers to 2Gor 3G 3GPP access networks, roaming, authentication, bearer managementfunctions including dedicated bearer establishment, support for publicwarning system (PWS) (which includes earthquake and tsunami warningsystem (ETWS) and commercial mobile alert system (CMAS)) messagetransmission. The S-GW host provides assorted functions includingper-user based packet filtering (by e.g., deep packet inspection),lawful interception, UE Internet protocol (IP) address allocation,transport level packet marking in the DL, UL and DL service levelcharging, gating and rate enforcement, DL rate enforcement based onaccess point name aggregate maximum bit rate (APN-AMBR).

Interfaces for transmitting user traffic or control traffic may be used.The UE 10 is connected to the eNB 20 via a Uu interface. The eNBs 20 areconnected to each other via an X2 interface. Neighboring eNBs may have ameshed network structure that has the X2 interface. A plurality of nodesmay be connected between the eNB 20 and the gateway 30 via an S1interface.

FIG. 2 shows a block diagram of architecture of a typical E-UTRAN and atypical EPC. Referring to FIG. 2, the eNB 20 may perform functions ofselection for gateway 30, routing toward the gateway 30 during a radioresource control (RRC) activation, scheduling and transmitting of pagingmessages, scheduling and transmitting of broadcast channel (BCH)information, dynamic allocation of resources to the UEs 10 in both ULand DL, configuration and provisioning of eNB measurements, radio bearercontrol, radio admission control (RAC), and connection mobility controlin LTE ACTIVE state. In the EPC, and as noted above, gateway 30 mayperform functions of paging origination, LTE IDLE state management,ciphering of the user plane, SAE bearer control, and ciphering andintegrity protection of NAS signaling.

FIG. 3 shows a block diagram of a user plane protocol stack of an LTEsystem. FIG. 4 shows a block diagram of a control plane protocol stackof an LTE system. Layers of a radio interface protocol between the UEand the E-UTRAN may be classified into a first layer (L1), a secondlayer (L2), and a third layer (L3) based on the lower three layers ofthe open system interconnection (OSI) model that is well-known in thecommunication system.

A physical (PHY) layer belongs to the L1. The PHY layer provides ahigher layer with an information transfer service through a physicalchannel. The PHY layer is connected to a medium access control (MAC)layer, which is a higher layer of the PHY layer, through a transportchannel. A physical channel is mapped to the transport channel. Databetween the MAC layer and the PHY layer is transferred through thetransport channel. Between different PHY layers, i.e., between a PHYlayer of a transmission side and a PHY layer of a reception side, datais transferred via the physical channel.

A MAC layer, a radio link control (RLC) layer, and a packet dataconvergence protocol (PDCP) layer belong to the L2. The MAC layerprovides services to the RLC layer, which is a higher layer of the MAClayer, via a logical channel. The MAC layer provides data transferservices on logical channels. The RLC layer supports the transmission ofdata with reliability. Meanwhile, a function of the RLC layer may beimplemented with a functional block inside the MAC layer. In this case,the RLC layer may not exist. The PDCP layer provides a function ofheader compression function that reduces unnecessary control informationsuch that data being transmitted by employing IP packets, such as IPv4or IPv6, can be efficiently transmitted over a radio interface that hasa relatively small bandwidth.

A radio resource control (RRC) layer belongs to the L3. The RLC layer islocated at the lowest portion of the L3, and is only defined in thecontrol plane. The RRC layer controls logical channels, transportchannels, and physical channels in relation to the configuration,reconfiguration, and release of radio bearers (RBs). The RB signifies aservice provided the L2 for data transmission between the UE andE-UTRAN.

Referring to FIG. 3, the RLC and MAC layers (terminated in the eNB onthe network side) may perform functions such as scheduling, automaticrepeat request (ARQ), and hybrid ARQ (HARQ). The PDCP layer (terminatedin the eNB on the network side) may perform the user plane functionssuch as header compression, integrity protection, and ciphering.

Referring to FIG. 4, the RLC and MAC layers (terminated in the eNB onthe network side) may perform the same functions for the control plane.The RRC layer (terminated in the eNB on the network side) may performfunctions such as broadcasting, paging, RRC connection management, RBcontrol, mobility functions, and UE measurement reporting andcontrolling. The NAS control protocol (terminated in the MME of gatewayon the network side) may perform functions such as a SAE bearermanagement, authentication, LTE IDLE mobility handling, pagingorigination in LTE IDLE, and security control for the signaling betweenthe gateway and UE.

FIG. 5 shows an example of a physical channel structure. A physicalchannel transfers signaling and data between PHY layer of the UE and eNBwith a radio resource. A physical channel consists of a plurality ofsubframes in time domain and a plurality of subcarriers in frequencydomain. One subframe, which is 1 ms, consists of a plurality of symbolsin the time domain. Specific symbol(s) of the subframe, such as thefirst symbol of the subframe, may be used for a physical downlinkcontrol channel (PDCCH). The PDCCH carries dynamic allocated resources,such as a physical resource block (PRB) and modulation and coding scheme(MCS).

A DL transport channel includes a broadcast channel (BCH) used fortransmitting system information, a paging channel (PCH) used for paginga UE, a downlink shared channel (DL-SCH) used for transmitting usertraffic or control signals, a multicast channel (MCH) used for multicastor broadcast service transmission. The DL-SCH supports HARQ, dynamiclink adaptation by varying the modulation, coding and transmit power,and both dynamic and semi-static resource allocation. The DL-SCH alsomay enable broadcast in the entire cell and the use of beamforming.

A UL transport channel includes a random access channel (RACH) normallyused for initial access to a cell, an uplink shared channel (UL-SCH) fortransmitting user traffic or control signals, etc. The UL-SCH supportsHARQ and dynamic link adaptation by varying the transmit power andpotentially modulation and coding. The UL-SCH also may enable the use ofbeamforming.

The logical channels are classified into control channels fortransferring control plane information and traffic channels fortransferring user plane information, according to a type of transmittedinformation. That is, a set of logical channel types is defined fordifferent data transfer services offered by the MAC layer.

The control channels are used for transfer of control plane informationonly. The control channels provided by the MAC layer include a broadcastcontrol channel (BCCH), a paging control channel (PCCH), a commoncontrol channel (CCCH), a multicast control channel (MCCH) and adedicated control channel (DCCH). The BCCH is a downlink channel forbroadcasting system control information. The PCCH is a downlink channelthat transfers paging information and is used when the network does notknow the location cell of a UE. The CCCH is used by UEs having no RRCconnection with the network. The MCCH is a point-to-multipoint downlinkchannel used for transmitting multimedia broadcast multicast services(MBMS) control information from the network to a UE. The DCCH is apoint-to-point bi-directional channel used by UEs having an RRCconnection that transmits dedicated control information between a UE andthe network.

Traffic channels are used for the transfer of user plane informationonly. The traffic channels provided by the MAC layer include a dedicatedtraffic channel (DTCH) and a multicast traffic channel (MTCH). The DTCHis a point-to-point channel, dedicated to one UE for the transfer ofuser information and can exist in both uplink and downlink. The MTCH isa point-to-multipoint downlink channel for transmitting traffic datafrom the network to the UE.

Uplink connections between logical channels and transport channelsinclude the DCCH that can be mapped to the UL-SCH, the DTCH that can bemapped to the UL-SCH and the CCCH that can be mapped to the UL-SCH.Downlink connections between logical channels and transport channelsinclude the BCCH that can be mapped to the BCH or DL-SCH, the PCCH thatcan be mapped to the PCH, the DCCH that can be mapped to the DL-SCH, andthe DTCH that can be mapped to the DL-SCH, the MCCH that can be mappedto the MCH, and the MTCH that can be mapped to the MCH.

An RRC state indicates whether an RRC layer of the UE is logicallyconnected to an RRC layer of the E-UTRAN. The RRC state may be dividedinto two different states such as an RRC idle state (RRC_IDLE) and anRRC connected state (RRC_CONNECTED). In RRC_IDLE, the UE may receivebroadcasts of system information and paging information while the UEspecifies a discontinuous reception (DRX) configured by NAS, and the UEhas been allocated an identification (ID) which uniquely identifies theUE in a tracking area and may perform public land mobile network (PLMN)selection and cell re-selection. Also, in RRC_IDLE, no RRC context isstored in the eNB.

In RRC_CONNECTED, the UE has an E-UTRAN RRC connection and a context inthe E-UTRAN, such that transmitting and/or receiving data to/from theeNB becomes possible. Also, the UE can report channel qualityinformation and feedback information to the eNB. In RRC_CONNECTED, theE-UTRAN knows the cell to which the UE belongs. Therefore, the networkcan transmit and/or receive data to/from UE, the network can controlmobility (handover and inter-radio access technologies (RAT) cell changeorder to GSM EDGE radio access network (GERAN) with network assistedcell change (NACC)) of the UE, and the network can perform cellmeasurements for a neighboring cell.

In RRC_IDLE, the UE specifies the paging DRX cycle. Specifically, the UEmonitors a paging signal at a specific paging occasion of every UEspecific paging DRX cycle. The paging occasion is a time interval duringwhich a paging signal is transmitted. The UE has its own pagingoccasion. A paging message is transmitted over all cells belonging tothe same tracking area. If the UE moves from one tracking area (TA) toanother TA, the UE will send a tracking area update (TAU) message to thenetwork to update its location.

Vehicle-to-everything (V2X) communication is described. V2Xcommunication contains three different types, which arevehicle-to-vehicle (V2V) communications, vehicle-to-infrastructure (V2I)communications, and vehicle-to-pedestrian (V2P) communications. Thesethree types of V2X can use “co-operative awareness” to provide moreintelligent services for end-users. This means that transport entities,such as vehicles, roadside infrastructure, and pedestrians, can collectknowledge of their local environment (e.g. information received fromother vehicles or sensor equipment in proximity) to process and sharethat knowledge in order to provide more intelligent services, such ascooperative collision warning or autonomous driving.

V2X service is a type of communication service that involves atransmitting or receiving UE using V2V application via 3GPP transport.Based on the other party involved in the communication, it can befurther divided into V2V service, V2I service, V2P service, and V2Nservice. V2V service is a type of V2X service, where both parties of thecommunication are UEs using V2V application. V21 service is a type ofV2X Service, where one party is a UE and the other party is a road sideunit (RSU) both using V2I application. The RSU is an entity supportingV2I service that can transmit to, and receive from a UE using V2Iapplication. RSU is implemented in an eNB or a stationary UE. V2Pservice is a type of V2X service, where both parties of thecommunication are UEs using V2P application. V2N service is a type ofV2X service, where one party is a UE and the other party is a servingentity, both using V2N applications and communicating with each othervia LTE network entities.

For V2V, E-UTRAN allows such UEs that are in proximity of each other toexchange V2V-related information using E-UTRA(N) when permission,authorization and proximity criteria are fulfilled. The proximitycriteria can be configured by the mobile network operator (MNO).However, UEs supporting V2V service can exchange such information whenserved by or not served by E-UTRAN which supports V2X Service. The UEsupporting V2V applications transmits application layer information(e.g. about its location, dynamics, and attributes as part of the V2Vservice). The V2V payload must be flexible in order to accommodatedifferent information contents, and the information can be transmittedperiodically according to a configuration provided by the MNO. V2V ispredominantly broadcast-based. V2V includes the exchange of V2V-relatedapplication information between distinct UEs directly and/or, due to thelimited direct communication range of V2V, the exchange of V2V-relatedapplication information between distinct UEs via infrastructuresupporting V2X service, e.g., RSU, application server, etc.

For V2I, the UE supporting V2I applications sends application layerinformation to RSU. RSU sends application layer information to a groupof UEs or a UE supporting V2I applications. V2N is also introduced whereone party is a UE and the other party is a serving entity, bothsupporting V2N applications and communicating with each other via LTEnetwork.

For V2P, E-UTRAN allows such UEs that are in proximity of each other toexchange V2P-related information using E-UTRAN when permission,authorization and proximity criteria are fulfilled. The proximitycriteria can be configured by the MNO. However, UEs supporting V2Pservice can exchange such information even when not served by E-UTRANwhich supports V2X Service. The UE supporting V2P applications transmitsapplication layer information. Such information can be broadcast by avehicle with UE supporting V2X service (e.g., warning to pedestrian),and/or by a pedestrian with UE supporting V2X service (e.g., warning tovehicle). V2P includes the exchange of V2P-related applicationinformation between distinct UEs (one for vehicle and the other forpedestrian) directly and/or, due to the limited direct communicationrange of V2P, the exchange of V2P-related application informationbetween distinct UEs via infrastructure supporting V2X service, e.g.,RSU, application server, etc.

FIG. 6 shows an example of an architecture for V2X communication.Referring to FIG. 6, the existing node (i.e. eNB/MME) or new nodes maybe deployed for supporting V2X communication. The interface betweennodes may be S1/X2 interface or new interface. That is, the interfacebetween eNB1 and eNB2 may be X2 interface or new interface. Theinterface between eNB1/eNB2 and MME1/MME2 may be S1 interface or newinterface.

Further, there may be three types of UE for V2X communication, one ofwhich is a vehicle UE, the second is a RSU UE, and the last is apedestrian UE. The vehicle UE may be like the generic UE. The RSU UE isa RSU which is implemented in the UE, and can relay or multicast orbroadcast the traffic or safety information or other vehicle UEs. Thepedestrian UE is a UE supporting V2X communication which is carried by apedestrian, cyclist, driver or passenger. For V2X communication, vehicleUEs and pedestrian UEs may be communicated with each other directly viaPC5 interface. Alternatively, vehicle UEs and pedestrian UEs may becommunicated with each other indirectly via the network node. Thenetwork node may be one of an eNB, a new entity for V2X communication, anew gateway for V2X communication, a RSU, etc. The network node may notbe the MME or S-GW. Alternatively, a vehicle UE or a pedestrian UE maybroadcast data, and the RSU UE may receive the broadcast data. The RSUand another vehicle UE/pedestrian UE may be communicated with each otherindirectly via the network node. The network node may be one of an eNB,a new entity for V2X communication, a new gateway for V2X communication,a RSU, etc. In this case, the network node may not be the MME or S-GW.

Authorization is an issue to solve from eNB point of view. The eNB mayhave to decide how to handle the radio resource to the corresponding UE.More specifically, depending on the type of UEs supporting V2Xcommunication, the eNB may allocate radio resource differently. Forexample, for pedestrian UE, the eNB may decide to use mode 4 sidelinktransmission. In the mode 4 sidelink transmission, the pedestrian UE mayperform partial sensing on a subset of subframes, not entire subframes.In this case, the pedestrian UE can apply partial sensing to save power.Accordingly, it may be required to solve the authentication problem forthe vehicle UE, RSU UE and pedestrian UE. In addition, it may berequired to solve the authentication problem at the target eNB sideduring mobility procedure.

FIG. 7 shows a method for receiving authorization information for V2Xcommunication according to an embodiment of the present invention.

In step S100, the eNB receives authorization information for apedestrian UE which indicates whether a UE is authorized as thepedestrian UE. The authorization information for the pedestrian UE maybe “Pedestrian UE Authorized” information element (IE), which may beincluded in an existing message or a new message. The authorizationinformation for the pedestrian UE (or “Pedestrian UE Authorized” IE)provides information on the authorization status of the UE as thepedestrian UE for V2X services. That is, the authorization informationfor the pedestrian UE indicates whether the UE is authorized aspedestrian UE or not. Table 1 shows an example of “Pedestrian UEAuthorized” IE.

TABLE 1 IE/Group Pres- IE type and Semantics Name ence Range referencedescription Pedestrian UE O ENUMERATED Indicates whether Authorized(authorized, the UE is authorized not authorized, for Pedestrian UE . ..) or not

Referring to Table 1, “Pedestrian UE Authorized” IE indicates whetherthe UE is authorized for pedestrian UE or not.

Further, the UE may receive authorization information for the vehicleUE, together with the authorization information for the pedestrian UE.The authorization information for the vehicle UE may be “Vehicle UEAuthorized” IE, which may be included in an existing message or a newmessage. The authorization information for the vehicle UE (or “VehicleUE Authorized” IE) provides information on the authorization status ofthe UE as the vehicle UE for V2X services. That is, the authorizationinformation for the vehicle UE indicates whether the UE is authorized asvehicle UE or not. Table 2 shows an example of “Vehicle UE Authorized”IE.

TABLE 2 IE/Group Pres- IE type and Semantics Name ence Range referencedescription Vehicle UE O ENUMERATED Indicates whether Authorized(authorized, the UE is authorized not authorized, for Vehicle UE or . ..) not

Referring to Table 2, “Vehicle UE Authorized” IE indicates whether theUE is authorized for vehicle UE or not.

Further, the UE may receive authorization information for the RSU UE,together with the authorization information for the pedestrianUE/vehicle UE. The authorization information for the RSU UE may be “RSUUE Authorized” IE, which may be included in an existing message or a newmessage. The authorization information for the RSU UE (or “RSU UEAuthorized” IE) provides information on the authorization status of theUE as the RSU UE for V2X services. That is, the authorizationinformation for the RSU UE indicates whether the UE is authorized as RSUUE or not. Table 3 shows an example of “RSU UE Authorized” IE.

TABLE 3 IE/Group Pres- IE type and Semantics Name ence Range referencedescription RSU UE O ENUMERATED Indicates whether Authorized(authorized, the UE is authorized not authorized, for RSU UE or not . ..)

Referring to Table 3, “RSU UE Authorized” IE indicates whether the UE isauthorized for vehicle UE or not.

Upon receiving the authorization information for at least one ofpedestrian UE, vehicle UE or RSU UE, the eNB may authorize the UE as thepedestrian UE or not according to the received authorizationinformation. If the UE is authorized as the pedestrian UE, the eNB mayupdate authorization of the UE for a V2X service as the pedestrian UE.If the UE is not authorized as the pedestrian UE, the eNB may initiateactions to ensure that the UE is no longer accessing a V2X service asthe pedestrian UE.

The authorization information for at least one of pedestrian UE, vehicleUE or RSU UE may be received during initial attach/service request stageor during the MME triggered UE context modification procedure. In thiscase, the authorization information for at least one of pedestrian UE,vehicle UE or RSU UE may be received from the MME. For example, theauthorization information for at least one of pedestrian UE, vehicle UEor RSU UE may be received during an initial context setup procedure insuch as attach, service request, etc., via an initial context setuprequest message. Alternatively, the authorization information for atleast one of pedestrian UE, vehicle UE or RSU UE may be received via aUE context modification request message.

Alternatively, the authorization information for at least one ofpedestrian UE, vehicle UE or RSU UE may be received during mobilityprocedure. For X2 handover procedure, the authorization information forat least one of pedestrian UE, vehicle UE or RSU UE may be received fromthe source eNB via the handover request message. Further, theauthorization information for at least one of pedestrian UE, vehicle UEor RSU UE may be updated and received from the MME via a path switchrequest acknowledge message. For S1 handover procedure, authorizationinformation for at least one of pedestrian UE, vehicle UE or RSU UE maybe received from the MME via the handover request message.

Hereinafter, various embodiments of the present invention for receivingthe authorization information for at least one of pedestrian UE, vehicleUE or RSU UE and using the received authorization information aredescribed.

FIG. 8 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.This embodiment corresponds authentication during initial attach/servicerequest, specifically the procedure involving the initial context setupprocedure in such as attach, service request, etc.

In step S200, the eNB receives an initial context setup request messagefrom the MME. The initial context setup request message is sent by theMME to request the setup of a UE context. The initial context setuprequest message may include the authorization information for thepedestrian UE, i.e. “Pedestrian UE Authorized” IE. Further, even thoughnot described, the initial context setup request message may include atleast one of the authorization information for the vehicle UE, i.e.“Vehicle UE Authorized” IE, or the authorization information for the RSUUE, i.e. “RSU UE Authorized” IE. Table 4 shows an example of the initialcontext setup request message according to an embodiment of the presentinvention.

TABLE 4 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type M 9.2.1.1 YESreject MME UE S1AP M 9.2.3.3 YES reject ID eNB UE S1AP ID M 9.2.3.4 YESreject UE Aggregate M 9.2.1.20 YES reject Maximum Bit Rate E-RAB to Be 1YES reject Setup List >E-RAB to Be 1 . . . <maxnoofE- EACH reject SetupItem IEs RABs> >>E-RAB ID M 9.2.1.2 — >>E-RAB Level M 9.2.1.15 Includes— QoS necessary Parameters QoS parameters. >>Transport M 9.2.2.1 — LayerAddress >>GTP-TEID M 9.2.2.2 — >>NAS-PDU O 9.2.3.5 — >>Correlation O9.2.1.80 YES ignore ID >>SIPTO O Correlation YES ignore Correlation IDID 9.2.1.80 UE Security M 9.2.1.40 YES reject Capabilities Security KeyM 9.2.1.41 The KeNB is YES reject provided after the key- generation inthe MME, see TS 33.401 [15]. Trace Activation O 9.2.1.4 YES ignoreHandover O 9.2.1.22 YES ignore Restriction List UE Radio O 9.2.1.27 YESignore Capability Subscriber Profile O 9.2.1.39 YES ignore ID forRAT/Frequency priority CS Fallback O 9.2.3.21 YES reject Indicator SRVCCOperation O 9.2.1.58 YES ignore Possible CSG Membership O 9.2.1.73 YESignore Status Registered LAI O 9.2.3.1 YES ignore GUMMEI O 9.2.3.9 ThisIE YES ignore indicates the MME serving the UE. MME UE S1AP O 9.2.3.3This IE YES ignore ID 2 indicates the MME UE S1AP ID assigned by theMME. Management O 9.2.1.83 YES ignore Based MDT Allowed Management O MDTYES ignore Based MDT PLMN PLMN List List 9.2.1.89 Additional CS C-9.2.3.37 YES ignore Fallback Indicator ifCSFBhigh priority Masked IMEISVO 9.2.3.38 YES ignore Expected UE O 9.2.1.96 YES ignore Behaviour ProSeAuthorized O 9.2.1.99 YES ignore Vehicle UE O 9.2.1.XX YES ignoreAuthorized RSU UE O 9.2.1.XX YES ignore Authorized Pedestrian UE O9.2.1.XX YES ignore Authorized

Referring to Table 4, the initial context setup request message mayinclude at least one of “Pedestrian UE Authorized” IE, shown in Table 1above, “Vehicle UE Authorized” IE, shown in Table 2 above, or “RSU UEAuthorized” IE, shown in Table 3 above.

Upon receipt of the initial context setup request message including atleast one “Pedestrian UE Authorized” IE, “Vehicle UE Authorized” IE or“RSU UE Authorized” IE, the eNB may store the received authorizationinformation, if supported, in the UE context. The eNB may validatewhether the UE is authorized as pedestrian UE, vehicle UE, or RSU UE forV2X communication transmission by using the UE context. In step S201,the eNB transmits an initial context setup response message to the MME.

FIG. 9 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.This embodiment corresponds to authentication during the MME triggeredUE context modification procedure.

In step S300, the eNB receives a UE context modification request messagefrom the MME. The UE context modification request message is sent by theMME to provide UE context information changes to the eNB. The UE contextmodification request message may include the authorization informationfor the pedestrian UE, i.e. “Pedestrian UE Authorized” IE. Further, eventhough not described, the UE context modification request message mayinclude at least one of the authorization information for the vehicleUE, i.e. “Vehicle UE Authorized” IE, or the authorization informationfor the RSU UE, i.e. “RSU UE Authorized” IE. Table 5 shows an example ofthe UE context modification request message according to an embodimentof the present invention.

TABLE 5 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type M 9.2.1.1 YESreject MME UE S1AP M 9.2.3.3 YES reject ID eNB UE S1AP ID M 9.2.3.4 YESreject Security Key O 9.2.1.41 A fresh KeNB is YES reject provided afterperforming a key- change on the fly procedure in the MME, see TS 33.401[15]. Subscriber Profile O 9.2.1.39 YES ignore ID for RAT/Frequencypriority UE Aggregate O 9.2.1.20 YES ignore Maximum Bit Rate CS FallbackO 9.2.3.21 YES reject Indicator UE Security O 9.2.1.40 YES rejectCapabilities CSG Membership O 9.2.1.73 YES ignore Status Registered LAIO 9.2.3.1 YES ignore Additional CS C- 9.2.3.37 YES ignore FallbackIndicator ifCSFB highpriority ProSe Authorized O 9.2.1.99 YES ignoreVehicle UE O 9.2.1.XX YES ignore Authorized RSU UE O 9.2.1.XX YES ignoreAuthorized Pedestrian UE O 9.2.1.XX YES ignore Authorized

Referring to Table 5, the UE context modification request message mayinclude at least one of “Pedestrian UE Authorized” IE, shown in Table 1above, “Vehicle UE Authorized” IE, shown in Table 2 above, or “RSU UEAuthorized” IE, shown in Table 3 above.

If “Pedestrian UE Authorized” IE, “Vehicle UE Authorized” IE or “RSU UEAuthorized” IE is contained in the UE context modification requestmessage, the eNB may, if supported, update its authorization informationfor the corresponding UE accordingly. If “Pedestrian UE Authorized” IE,“Vehicle UE Authorized” IE or “RSU UE Authorized” IE is set to “notauthorized”, the eNB may, if supported, initiate actions to ensure thatthe corresponding UE is no longer accessing the relevant V2X services.In step S301, the eNB transmits an UE context modification responsemessage to the MME.

FIG. 10 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.This embodiment corresponds to authentication during mobility procedure,specifically X2 handover procedure.

In step S400, the target eNB receives a handover request message fromthe source eNB. The handover request message is sent by the source eNBto the target eNB to request the preparation of resources for ahandover. The handover request message may include the authorizationinformation for the pedestrian UE, i.e. “Pedestrian UE Authorized” IE.Further, even though not described, the UE context modification requestmessage may include at least one of the authorization information forthe vehicle UE, i.e. “Vehicle UE Authorized” IE, or the authorizationinformation for the RSU UE, i.e. “RSU UE Authorized” IE. Table 6 showsan example of the handover request message according to an embodiment ofthe present invention.

TABLE 6 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type M 9.2.13 YESreject Old eNB UE X2AP M eNB UE Allocated at YES reject ID X2AP thesource ID eNB 9.2.24 Cause M 9.2.6 YES ignore Target Cell ID M ECG1 YESreject 9.2.14 GUMMEI M 9.2.16 YES reject UE Context 1 YES rejectInformation >MME UE S1AP M INTEGER MME UE — — ID (0 . . . 2³² S1AP ID−1) allocated at the MME >UE Security M 9.2.29 — — Capabilities >ASSecurity M 9.2.30 — — Information >UE Aggregate M 9.2.12 — — Maximum BitRate >Subscriber Profile O 9.2.25 — — ID for RAT/Frequencypriority >E-RABs To Be 1 — — Setup List >>E-RABs To Be 1 . . .<maxnoofBearers> EACH ignore Setup Item >>>E-RAB ID M 9.2.23 —— >>>E-RAB M 9.2.9 Includes — — Level QoS necessary Parameters QoSparameters >>>DL O 9.2.5 — — Forwarding >>>UL GTP M GTP SGW — — TunnelTunnel endpoint of Endpoint Endpoint the S1 9.2.1 transport bearer. Fordelivery of UL PDUs. >RRC Context M OCTET Includes the — — STRING RRCHandover Preparation Information message as defined in subclause 10.2.2of TS 36.331 [9] >Handover O 9.2.3 — — Restriction List >Location O9.2.21 Includes the — — Reporting necessary Information parameters forlocation reporting >Management O 9.2.59 YES ignore Based MDTAllowed >Management O MDT YES ignore Based MDT PLMN PLMN List List9.2.64 UE History M 9.2.38 Same YES ignore Information definition as inTS 36.413 [4] Trace Activation O 9.2.2 YES ignore SRVCC Operation O9.2.33 YES ignore Possible CSG Membership O 9.2.52 YES reject StatusMobility O BIT Information YES ignore Information STRING related to the(SIZE handover; the (32)) source eNB provides it in order to enablelater analysis of the conditions that led to a wrong HO. Masked IMEISV O9.2.69 YES ignore UE History O OCTET VisitedCellInfo YES ignoreInformation from the STRING List UE contained in the UEInformationResponse message (TS 36.331 [9]) Expected UE O 9.2.70 YES ignoreBehaviour ProSe Authorized O 9.2.78 YES ignore Vehicle UE O 9.2.XX YESignore Authorized RSU UE O 9.2.XX YES ignore Authorized Pedestrian UE O9.2.1.XX YES ignore Authorized

Referring to Table 6, the handover request message may include at leastone of “Pedestrian UE Authorized” IE, shown in Table 1 above, “VehicleUE Authorized” IE, shown in Table 2 above, or “RSU UE Authorized” IE,shown in Table 3 above.

If “Pedestrian UE Authorized”, “Vehicle UE Authorized” IE or “RSU UEAuthorized” IE is contained in the handover request message, and itcontains one or more IEs set to “authorized”, the target eNB may, ifsupported, consider that the corresponding UE is authorized for therelevant V2X services. In step S401, the target eNB transmits a handoverrequest acknowledge message to the source eNB.

FIG. 11 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.During the X2 handover procedure, the authorization information forpedestrian UE, vehicle UE or RSU UE may be updated in some case. Thisembodiment corresponds to update of authentication during mobilityprocedure, specifically X2 handover procedure.

In step S500, the eNB transmits a path switch request message to theMME. In step S501, the eNB receives a path switch request acknowledgemessage from the MME. The path switch request acknowledge message issent by the MME to inform the eNB that the path switch has beensuccessfully completed in the EPC. The path switch request acknowledgemessage may include the authorization information for the pedestrian UE,i.e. “Pedestrian UE Authorized” IE. Further, even though not described,the path switch request acknowledge message may include at least one ofthe authorization information for the vehicle UE, i.e. “Vehicle UEAuthorized” IE, or the authorization information for the RSU UE, i.e.“RSU UE Authorized” IE. Table 7 shows an example of the handover requestmessage according to an embodiment of the present invention.

TABLE 7 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type M 9.2.1.1 YESreject MME UE S1AP ID M 9.2.3.3 YES ignore eNB UE S1AP ID M 9.2.3.4 YESignore UE Aggregate O 9.2.1.20 YES ignore Maximum Bit Rate E-RAB To Be 0. . . 1 YES ignore Switched in Uplink List >E-RABs Switched 1 . . .<maxnoofE- EACH ignore in Uplink Item IEs RABs> >>E-RAB ID M 9.2.1.2— >>Transport M 9.2.2.1 — Layer Address >>GTP-TEID M 9.2.2.2 — E-RAB ToBe O E-RAB A value for YES ignore Released List List E-RAB ID 9.2.1.36shall only be present once in E- RAB To Be Switched in Uplink List IEand E- RAB to Be Released List IE. Security Context M 9.2.1.26 One pairof YES reject {NCC, NH} is provided. Criticality O 9.2.1.21 YES ignoreDiagnostics MME UE S1AP ID 2 O 9.2.3.3 This IE YES ignore indicates theMME UE S1AP ID assigned by the MME. CSG Membership O 9.2.1.73 YES ignoreStatus ProSe Authorized O 9.2.1.99 YES ignore Vehicle UE O 9.2.1.XX YESignore Authorized RSU UE O 9.2.1.XX YES ignore Authorized Pedestrian UEO 9.2.1.XX YES ignore Authorized

Referring to Table 7, the path switch request acknowledge message mayinclude at least one of “Pedestrian UE Authorized” IE, shown in Table 1above, “Vehicle UE Authorized” IE, shown in Table 2 above, or “RSU UEAuthorized” IE, shown in Table 3 above.

If “Pedestrian UE Authorized”, “Vehicle UE Authorized” IE or “RSU UEAuthorized” IE is contained in the path switch request acknowledgemessage, the eNB may, if supported, update its authorization informationfor the corresponding UE accordingly. If “Pedestrian UE Authorized”,“Vehicle UE Authorized” IE or “RSU UE Authorized” IE is set to “notauthorized”, the eNB may, if supported, initiate actions to ensure thatthe corresponding UE is no longer accessing the relevant V2X services.

FIG. 12 shows a method for receiving authorization information for V2Xcommunication according to another embodiment of the present invention.This embodiment corresponds to authentication during mobility procedure,specifically S1 handover procedure.

In step S600, the target eNB receives a handover request message fromthe MME. The handover request message is sent by the MME to the targeteNB to request the preparation of resources. The handover requestmessage may include the authorization information for the pedestrian UE,i.e. “Pedestrian UE Authorized” IE. Further, even though not described,the UE context modification request message may include at least one ofthe authorization information for the vehicle UE, i.e. “Vehicle UEAuthorized” IE, or the authorization information for the RSU UE, i.e.“RSU UE Authorized” IE. Table 8 shows an example of the handover requestmessage according to an embodiment of the present invention.

TABLE 8 IE type and Semantics Assigned IE/Group Name Presence Rangereference description Criticality Criticality Message Type M 9.2.1.1 YESreject MME UE S1AP ID M 9.2.3.3 YES reject Handover Type M 9.2.1.13 YESreject Cause M 9.2.1.3 YES ignore UE Aggregate M 9.2.1.20 YES rejectMaximum Bit Rate E-RABs To Be 1 YES reject Setup List >E-RABs To Be 1 .. . <maxnoofE- EACH reject Setup Item IEs RABs> >>E-RAB ID M 9.2.1.2— >>Transport M 9.2.2.1 — Layer Address >>GTP-TEID M 9.2.2.2 To deliverUL — PDUs. >>E-RAB Level M 9.2.1.15 Includes — QoS Parameters necessaryQoS parameters. >>Data O 9.2.1.76 YES ignore Forwarding Not PossibleSource to Target M 9.2.1.56 YES reject Transparent Container UE SecurityM 9.2.1.40 YES reject Capabilities Handover O 9.2.1.22 YES ignoreRestriction List Trace Activation O 9.2.1.4 YES ignore Request Type O9.2.1.34 YES ignore SRVCC Operation O 9.2.1.58 YES ignore PossibleSecurity Context M 9.2.1.26 YES reject NAS Security C- 9.2.3.31 The eNBshall YES reject Parameters to E- iffrom use this IE as UTRAN UTRANGERANspecified in TS 33.401 [15]. CSG Id O 9.2.1.62 YES reject CSG MembershipO 9.2.1.73 YES ignore Status GUMMEI O 9.2.3.9 This IE YES ignoreindicates the MME serving the UE. MME UE S1AP ID 2 O 9.2.3.3 This IE YESignore indicates the MME UE S1AP ID assigned by the MME. ManagementBased O 9.2.1.83 YES ignore MDT Allowed Management Based O MDT YESignore MDT PLMN List PLMN List 9.2.1.89 Masked IMEISV O 9.2.3.38 YESignore Expected UE O 9.2.1.96 YES ignore Behaviour ProSe Authorized O9.2.1.99 YES ignore Vehicle UE O 9.2.1.XX YES ignore Authorized RSU UE O9.2.1.XX YES ignore Authorized Pedestrian UE O 9.2.1.XX YES ignoreAuthorized

Referring to Table 8, the handover request message may include at leastone of “Pedestrian UE Authorized” IE, shown in Table 1 above, “VehicleUE Authorized” IE, shown in Table 2 above, or “RSU UE Authorized” IE,shown in Table 3 above.

If “Pedestrian UE Authorized” IE, “Vehicle UE Authorized” IE or “RSU UEAuthorized” IE is contained in the handover request message, and itcontains one or more IEs set to “authorized”, the target eNB may, ifsupported, consider that the corresponding UE is authorized for therelevant V2X services. In step S601, the target eNB transmits a handoverrequest acknowledge message to the MME.

FIG. 13 shows a communication system to implement an embodiment of thepresent invention.

An eNB 800 includes a processor 810, a memory 820 and a transceiver 830.The processor 810 may be configured to implement proposed functions,procedures and/or methods described in this description. Layers of theradio interface protocol may be implemented in the processor 810. Thememory 820 is operatively coupled with the processor 810 and stores avariety of information to operate the processor 810. The transceiver 830is operatively coupled with the processor 810, and transmits and/orreceives a radio signal.

A MME or another eNB 900 includes a processor 910, a memory 920 and atransceiver 930. The processor 910 may be configured to implementproposed functions, procedures and/or methods described in thisdescription. Layers of the radio interface protocol may be implementedin the processor 910. The memory 920 is operatively coupled with theprocessor 910 and stores a variety of information to operate theprocessor 910. The transceiver 930 is operatively coupled with theprocessor 910, and transmits and/or receives a radio signal.

The processors 810, 910 may include application-specific integratedcircuit (ASIC), other chipset, logic circuit and/or data processingdevice. The memories 820, 920 may include read-only memory (ROM), randomaccess memory (RAM), flash memory, memory card, storage medium and/orother storage device. The transceivers 830, 930 may include basebandcircuitry to process radio frequency signals. When the embodiments areimplemented in software, the techniques described herein can beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. The modules can be stored inmemories 820, 920 and executed by processors 810, 910. The memories 820,920 can be implemented within the processors 810, 910 or external to theprocessors 810, 910 in which case those can be communicatively coupledto the processors 810, 910 via various means as is known in the art.

According to the present invention, a pedestrian UE can be authorizedefficiently.

In view of the exemplary systems described herein, methodologies thatmay be implemented in accordance with the disclosed subject matter havebeen described with reference to several flow diagrams. While forpurposed of simplicity, the methodologies are shown and described as aseries of steps or blocks, it is to be understood and appreciated thatthe claimed subject matter is not limited by the order of the steps orblocks, as some steps may occur in different orders or concurrently withother steps from what is depicted and described herein. Moreover, oneskilled in the art would understand that the steps illustrated in theflow diagram are not exclusive and other steps may be included or one ormore of the steps in the example flow diagram may be deleted withoutaffecting the scope and spirit of the present disclosure.

What is claimed is:
 1. A method for receiving authorization informationfor vehicle-to-everything (V2X) communication by an eNodeB (eNB) in awireless communication system, the method comprising: receivingauthorization information for a pedestrian user equipment (UE) whichindicates whether a UE is authorized as the pedestrian UE.
 2. The methodof claim 1, further comprising receiving authorization information for avehicle UE which indicates whether the UE is authorized as the vehicleUE, together with the authorization information for the pedestrian UE.3. The method of claim 1, further comprising receiving authorizationinformation for a road side unit (RSU) UE which indicates whether the UEis authorized as the RSU UE, together with the authorization informationfor the pedestrian UE.
 4. The method of claim 1, further comprising:authorizing the UE as the pedestrian UE or not according to the receivedauthorization information; and deciding a resource allocation mode forthe authorized pedestrian UE.
 5. The method of claim 4, furthercomprising updating authorization of the UE for a V2X service as thepedestrian UE, if the UE is authorized as the pedestrian UE.
 6. Themethod of claim 4, further comprising initiating actions to ensure thatthe UE is no longer accessing a V2X service as the pedestrian UE, if theUE is not authorized as the pedestrian UE.
 7. The method of claim 1,wherein the authorization information for the pedestrian UE is receivedvia an initial context setup message or a UE context modificationrequest message from a mobility management entity (MME).
 8. The methodof claim 1, wherein the authorization information for the pedestrian UEis received via a handover request message from a MME.
 9. The method ofclaim 1, wherein the authorization information for the pedestrian UE isreceived via a path switch request acknowledge message from a MME. 10.The method of claim 1, wherein the authorization information for thepedestrian UE is received via a handover request message from a sourceeNB, and wherein the eNB is a target eNB.
 11. An eNodeB (eNB) in awireless communication system, the method comprising: a memory; and aprocessor, coupled to the memory, that: receives authorizationinformation for a pedestrian user equipment (UE) which indicates whethera UE is authorized as the pedestrian UE.
 12. The eNB of claim 11,wherein the processor further receives authorization information for avehicle UE which indicates whether the UE is authorized as the vehicleUE, together with the authorization information for the pedestrian UE.13. The eNB of claim 11, wherein the processor further receivesauthorization information for a road side unit (RSU) UE which indicateswhether the UE is authorized as the RSU UE, together with theauthorization information for the pedestrian UE.
 14. The eNB of claim11, wherein the processor further authorize the UE as the pedestrian UEor not according to the received authorization information.
 15. The eNBof claim 14, wherein the processor further update authorization of theUE for a vehicle-to-everything (V2X) service as the pedestrian UE, ifthe UE is authorized as the pedestrian UE.
 16. The eNB of claim 14,wherein the processor further initiate actions to ensure that the UE isno longer accessing a V2X service as the pedestrian UE, if the UE is notauthorized as the pedestrian UE.
 17. The eNB of claim 11, wherein theauthorization information for the pedestrian UE is received via aninitial context setup message or a UE context modification requestmessage from a mobility management entity (MME).
 18. The eNB of claim11, wherein the authorization information for the pedestrian UE isreceived via a handover request message from a MME.
 19. The eNB of claim11, wherein the authorization information for the pedestrian UE isreceived via a path switch request acknowledge message from a MME. 20.The eNB of claim 11, wherein the authorization information for thepedestrian UE is received via a handover request message from a sourceeNB, and wherein the eNB is a target eNB.